Semantic consistency

Characteristic Name:	Semantic consistency
Dimension:	Consistency
Description:	Data is semantically consistent
Granularity:	Element
Implementation Type:	Rule-based approach
Characteristic Type:	Declarative

Verification Metric:

The number of semantically inconsistent data reported per thousand records

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines:	Scenario:
Ensure that semantics of data is consistent within/across applications	(1) All orders placed by the customers are called “Sales order” in all tables/databases. (2) Anti-example: Payment type ( Check) Payment Details (Card type, Card number)
Maintenance of data dictionary or standard vocabularies of data semantics	(1) Data dictionary provides technical data as well as semantics of data

Validation Metric:

How mature is the creation and implementation of the DQ rules to maintain semantic consistency

These are examples of how the characteristic might occur in a database.

Example:	Source:
School admin: a student’s date of birth has the same value and format in the school register as that stored within the Student database.	N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.
A company has a color ﬁeld that only records red, blue, and yellow. A new requirement makes them decide to break each of these colors down to multiple shadings and thus institute a scheme of recording up to 30 different colors, all of which are variations of red, blue, and yellow. None of the old records are updated to the new scheme, as only new records use it. This data- base will have inconsistency of representation of color that crosses a point in time.	J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

Example:

Source:

School admin: a student’s date of birth has the same value and format in the school register as that stored within the Student database.

N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.

A company has a color ﬁeld that only records red, blue, and yellow. A new requirement makes them decide to break each of these colors down to multiple shadings and thus institute a scheme of recording up to 30 different colors, all of which are variations of red, blue, and yellow. None of the old records are updated to the new scheme, as only new records use it. This data- base will have inconsistency of representation of color that crosses a point in time.

J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition:	Source:
Data about an object or event in one data store is semantically Equivalent to data about the same object or event in another data store.	ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
Data is consistent if it doesn’t convey heterogeneity, neither in contents nor in form – anti examples: Order.Payment. Type = ‘Check’; Order. Payment. CreditCard_Nr = 4252… (inconsistency in contents); Order.requested_by: ‘European Central Bank’;Order.delivered_to: ‘ECB’ (inconsistency in form,because in the first case the customer is identified by the full name, while in the second case the customer’s acronym is used).	KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published.
The extent of consistency in using the same values (vocabulary control) and elements to convey the same concepts and meanings in an information object. This also includes the extent of semantic consistency among the same or different components of the object.	STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733.

Source quality

Characteristic Name:	Source quality
Dimension:	Reliability and Credibility
Description:	Data used is from trusted and credible sources
Granularity:	Information object
Implementation Type:	Process-based approach
Characteristic Type:	Usage

Verification Metric:

The number of tasks failed or under performed due to lack of source quality

The number of complaints received due to lack of source quality

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines:	Scenario:
Asses the reputation of data sources	(1) Central Bank is the best source to get daily exchange rates
Evaluate the remedies for non-compliance of data	(1) Any remedies given by the source organisation to mitigate the losses in case if the information is of low quality
Rely on shared information sources created\recommended\used by the organisations operating in the industry	(1) In performing portfolios analysis most organisations use the risk factors produced by a central body of the economy (Central bank)

Validation Metric:

How mature is the process to maintain quality of data sources

These are examples of how the characteristic might occur in a database.

Example:	Source:
Consider an inventory database that contains part numbers, warehouse locations, quantity on hand, and other information. However, it does not contain source information (where the parts came from). If a part is supplied by multiple suppliers, once the parts are received and put on the shelf there is no indication of which supplier the parts came from. The information in the database is always accurate and current. For normal inventory transactions and deci- sion making, the database is certainly of high quality. If a supplier reports that one of their shipments contained defective parts, this database is of no help in identifying whether they have any of those parts or not. The database is of poor quality because it does not contain a relevant element of information. Without that information, the database is poor data quality for the intended use.	J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

Example:

Source:

Consider an inventory database that contains part numbers, warehouse locations, quantity on hand, and other information. However, it does not contain source information (where the parts came from). If a part is supplied by multiple suppliers, once the parts are received and put on the shelf there is no indication of which supplier the parts came from. The information in the database is always accurate and current. For normal inventory transactions and deci- sion making, the database is certainly of high quality. If a supplier reports that one of their shipments contained defective parts, this database is of no help in identifying whether they have any of those parts or not. The database is of poor quality because it does not contain a relevant element of information. Without that information, the database is poor data quality for the intended use.

J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition:	Source:
The source of information (1) guarantees the quality of information it provides with remedies for non-compliance; (2) documents its certification in its Information Quality Management capabilities to capture, maintain, and deliver Quality Information; (3) provides objective and verifiable measures of the Quality of Information it provides in agreed-upon Quality Characteristics; and (4) guarantees that the Information has been protected from unauthorized access or modification.	ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
The notion of abstracting information into a data domain implies that there are enough users of the same set of data that it makes sense to manage their own versions. The dimension of enterprise agreement of usage measures the degree to which different organizations conform to the usage of the enterprise data domain of record instead of relying on their own data set.	LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub.
Reputation is the extent to which data are trusted or highly regarded in terms of their source or content.	SCANNAPIECO, M. & CATARCI, T. 2002. Data quality under a computer science perspective. Archivi & Computer, 2, 1-15.
The degree of reputation of an information object in a given community or culture.	STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733.
Data are trusted or highly regarded in terms of their source and content.	WANG, R. Y. & STRONG, D. M. 1996. Beyond accuracy: What data quality means to data consumers. Journal of management information systems, 5-33.